Content Model - Draft 01
Overview
In the following diagram we can see the current implemented content models for Stories and any referenced content models. It includes both web and mobile models and a proposed omnichannel content model. Its important to note the referenced models in the omnichannel proposal are region and product.
Current - Web
Current - Mobile
Proposed - Omni
Mixed
Considerations
- We have a strong link between stories and regions. This is so we are able to push particular pieces of content that are region specific. Our definition of a region is a large grouping such as Americas, Europe and Asia Pacific as well as more granular regions such as specific geo locations. This is so we have flexibility to push content to small areas which may cover multiple partner cafes / clubhouses and/or events.
- We have included the link between stories and products. It's important to do this now so we give the flexibility in the future for features such as shoppable images. Again as we are linking regions -> stories -> products we are able to write and push region specific stories or guides.
Questions
- Do we want to introduce the use of categories to the web? These are used in mobile and they should work for both platforms.
- Do we want to introduce the use of sub categories. This will in the long run make our search more specific and powerful.
- Do we need a seperate content model for videos? Do we feel like we would use the same video in multiple situations?
- Do we need a seperate content model for triptch. Do we use the same one across multiple products?
- Do we need a seperate content model for details and materials. Do we use the same one across multiple products?
Opportunities
- Regionalised content
- Shoppable content / images (regionalised)
- Omnichannel product launch content (regionalised)
- Clubhouse specific content (regionalised)
- Featured events on web and mobile (regionalised)